The Juniper router must be configured to automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-91143	JUNI-ND-000830	SV-101243r1_rule		Medium

Description
Automatic session termination addresses the termination of administrator-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever an administrator (or process acting on behalf of a user) accesses a network device. Such administrator sessions can be terminated (and thus terminate network administrator access) without terminating network sessions. Session termination terminates all processes associated with an administrator's logical session except those processes that are specifically created by the administrator (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. These conditions will vary across environments and network device types.

Description

Automatic session termination addresses the termination of administrator-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever an administrator (or process acting on behalf of a user) accesses a network device. Such administrator sessions can be terminated (and thus terminate network administrator access) without terminating network sessions. Session termination terminates all processes associated with an administrator's logical session except those processes that are specifically created by the administrator (i.e., session owner) to continue after the session is terminated. Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. These conditions will vary across environments and network device types.

STIG	Date
Juniper Router NDM Security Technical Implementation Guide	2019-07-01

Details

Check Text ( C-90297r2_chk )
Review the router configuration to verify that it is compliant with this requirement. As shown in the example below, a condition or event could be a period of inactivity such as 5 minutes for a specific user class. system { … … … } login { class ADMIN { idle-timeout 5; permissions admin-control; } } If the router is not configured to automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect, this is a finding.

Check Text ( C-90297r2_chk )

Review the router configuration to verify that it is compliant with this requirement. As shown in the example below, a condition or event could be a period of inactivity such as 5 minutes for a specific user class.

system {
…
…
…
}
login {
class ADMIN {
idle-timeout 5;
permissions admin-control;
}
}

If the router is not configured to automatically terminate a network administrator session after organization-defined conditions or trigger events requiring session disconnect, this is a finding.

Fix Text (F-97341r3_fix)
Set the idle timeout value for specific login classes to a value less than 10 minutes as shown in the example below. [edit system login] set class ADMIN idle-timeout 5